Understanding the current state application landscape starts with drawing the application system. This diagram contains, depending on witch of the above models used, all applications and their module structure, in- and external relations and / or detailed information about the transaction. All within the scope of the engagement.

In the Application Landscape three model types are distinguished:

• Application Model: provides an overview (diagrams and text) how the applications support processes in a static fashion.
  • Shows all applications in scope;
  • Stakeholders;
  • Impact;
  • Constraints.
• Application Interface Model: provides an overview (diagrams) and details (text) of all relevant interfaces between:
  • Internal applications amongst one another;
  • Internal applications and external systems.

Applications are linked to exchange information:

• • Why (especially in the As-Is)?
  • What (alignment of terminology)?
  • When (real-time, event driven, batch, working hours, etc.)?
  • How (manual, automatic, which infrastructure, etc.)?
• Transaction Model: shows how business transactions are handled in a number of steps and flow through various systems (internal and external) and possibly manual processes.
  • The Transaction Model shows how business transactions are handled in a number of steps and flow through various systems – internal and external – and possibly manual processes.

To determine the application landscape arrange a workshop:

Participants: IT manager (or delegate)

Input

• Information pack
• Process flow diagram

Execution

Understanding the current state application landscape starts with drawing the application system. This diagram contains, depending on witch of the above models used, all applications and their module structure, in- and external relations and / or detailed information about the transaction. All within the scope of the engagement.

Output

• Current State Application Landscape